Differential Dynamic Content Delivery With A Session Document Recreated In Dependence Upon An Interest Of An Identified User Participant

ABSTRACT

Differential dynamic content delivery, including creating a session document for a presentation, including identifying a user participant for the presentation, where the session document includes a session grammar and a session structured document, the user participant has a user profile comprising user classifications and user interests, the user interests comprising data fields for storing data values indicating user interest in one or more subjects of the presentation; receiving from the identified user participant at least one data value indicating user interest in one or more subjects of the presentation; storing in the user profile the data value indicating user interest; recreating the session document in dependence upon the data value indicating user interest; selecting from the recreated session document a classified structural element; and presenting the selected structural element to at least one user participant.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of and claims priority from U.S. patent application Ser. No. 11/095,796, filed on Mar. 31, 2005.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is data processing, or, more specifically, methods, systems, and products for differential dynamic content delivery.

2. Description of Related Art

Multimedia presentations through conferencing systems are becoming more common, but they are inflexible because all conference participants must be presented with exactly the same content. For any particular presentation, however, there is typically a wide variety of participant interest, company, group, or department membership, technical knowledge, security authorization, and so on, across almost any dimension in which participants may vary. Targeting content for such a heterogeneous set of users is typically a manual process today in which presenters create wholly separate presentations for each audience, and the content of each such presentation is reduced to the lowest common denominator of any particular audience. There is substantial need for improved multimedia presentation systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 sets forth a block diagram of an exemplary system architecture in which may be implemented various exemplary embodiments of the present invention.

FIG. 2 sets forth class diagrams for exemplary object oriented classes useful in implementing methods and systems for creating presentation documents according to various exemplary embodiments of the present invention.

FIG. 3 sets forth a data flow diagram illustrating a method for creating a presentation document.

FIG. 4 sets forth a data flow diagram illustrating an exemplary method of creating a presentation grammar.

FIG. 5 sets forth an exemplary data structure in which a full grammar may be implemented according to embodiments of the present invention.

FIG. 6 is a data flow diagram illustrating a further method for creating a presentation document.

FIG. 7 is a data flow diagram illustrating an exemplary method for classifying a structural element.

FIG. 8 sets forth a data flow diagram illustrating an exemplary method for classifying a structural element in a structured document.

FIG. 9 sets forth a data flow diagram illustrating a further exemplary method for classifying a structural element in a structured document.

FIG. 10 sets forth a data flow diagram illustrating another exemplary method for classifying a structural element in a structured document.

FIG. 11 sets forth a data flow diagram illustrating a further exemplary method for classifying a structural element in a structured document.

FIG. 12 sets forth a data flow diagram illustrating an exemplary method for creating a voice response grammar in a voice response server.

FIG. 13 sets forth a data flow diagram illustrating an exemplary method for creating a voice response grammar in a voice response server.

FIG. 14 is a data flow diagram illustrating an alternative exemplary method for creating a voice response grammar in a voice response server.

FIG. 15 is a data flow diagram illustrating another alternative exemplary method for creating a voice response grammar in a voice response server.

FIG. 16 sets forth a data flow diagram illustrating an exemplary method for creating a session document from a presentation document.

FIG. 17 sets forth a data flow diagram illustrating an exemplary method for amending a session document during a presentation.

FIG. 18 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery.

FIG. 19 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery with a planned agenda.

FIG. 20 sets forth a table illustrating a planned agenda.

FIG. 21 sets forth a chart illustrating an exemplary data structure useful for recording identities, durations, and sequence of presentation of presented structural elements.

FIG. 22 sets forth a bar chart illustrating an exemplary method of contrasting the durations and sequence of presented structural elements according to the planned agenda with the durations and sequence as recorded.

FIG. 23 sets forth a bar chart illustrating a further exemplary method of contrasting the durations and sequence of presented structural elements according to the planned agenda with the durations and sequence as recorded.

FIG. 24 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery with indications of interest from non-participants.

FIG. 25 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery with a session document recreated in dependence upon an interest of an identified user participant.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS Introduction

The present invention is described to a large extent in this specification in terms of methods for differential dynamic content delivery. Persons skilled in the art, however, will recognize that any computer system that includes suitable programming means for operating in accordance with the disclosed methods also falls well within the scope of the present invention. Suitable programming means include any means for directing a computer system to execute the steps of the method of the invention, including for example, systems comprised of processing units and arithmetic-logic circuits coupled to computer memory, which systems have the capability of storing in computer memory, which computer memory includes electronic circuits configured to store data and program instructions, programmed steps of the method of the invention for execution by a processing unit.

The invention also may be embodied in a computer program product, such as a diskette or other recording medium, for use with any suitable data processing system. Embodiments of a computer program product may be implemented by use of any recording medium for machine-readable information, including magnetic media, optical media, or other suitable media. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a program product. Persons skilled in the art will recognize immediately that, although most of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.

Creating a Presentation Document

Methods, systems, and products are now described for creating a presentation document with reference to the accompanying drawings, beginning with FIG. 1. FIG. 1 sets forth a block diagram of an exemplary system architecture in which may be implemented various exemplary embodiments of the present invention. The system of FIG. 1 include a content server (106) having stored content (108) of original documents from which presentation documents are created. Agent (110) includes software modules for creating presentation grammars for presentation documents according to content type (114) and for classifying presentation document content according to presentation attributes (116). Presentation attributes are generic selection criteria for displaying appropriate structural elements of original documents to users. Examples of presentation attributes include users' company names, department names, security levels, technical levels, and so on. User profiles (126) include user classification information typically used to filter presentation media according to presentation attributes.

Content server (106) includes storage for presentation documents (314) each of which is composed of a presentation grammar (120) and a structured document (122). A presentation grammar is a data structure that includes a set of key phrases used to identify presentation action identifiers and optional parameters for use in formulating presentation control instructions relevant to structural elements of a content type. In typical embodiments, presentation control instructions are represented by and formulated from presentation action identifiers (reference 518 on FIG. 5). Key phrases are spoken by users and presented as speech input to voice response server (104) where they are parsed and used to select a presentation action identifier (518 on FIG. 5) from a VRS grammar (105). VRS grammar (105) is formed dynamically from presentation grammars (120) in use in a presentation session (128). In some embodiments, VRS grammar (105) is formed dynamically from user grammars from user profiles (126). Presentation Session Control Language (“PSCL”) stream (132) represents a stream of presentation control instructions composed of presentation action identifiers (518 on FIG. 5) and optional presentation control parameters (520 on FIG. 5) from VRS (104) to presentation server (102) which is programmed to present (134) structured multimedia content (136) from structured documents (122) to users (124) in accordance with such presentation control instructions (132).

FIG. 2 sets forth class diagrams for exemplary object oriented classes useful in implementing methods and systems for creating presentation documents according to various exemplary embodiments of the present invention. FIG. 2 includes a presentation document class (314) that includes a reference to a presentation grammar (120), a reference to a structured document (122), and a network location (202) of an original document from which the presentation document was created. In the example of FIG. 2, the network location (202) of the original document is expressed as a Uniform Resource Identifier or “URI.”

FIG. 2 includes a profile class (126) whose objects represent presentation users. The profile class (126) includes a user name (204), a password (206), and a reference to a user grammar (208). A user grammar is a data structure that includes a set of key phrases that are used to select presentation action identifiers specific to a user for use in formulating presentation control instructions. For a presentation control instruction that instructs a presentation session to carry out the presentation action ‘page down,’ for example, an individual user may chose to associate with that presentation control instruction the key phrase “rock and roll” or “boogie on down” or any other key phrase favored by a user as will occur to those of skill in the art. Although these particular examples are somewhat fanciful, in fact, user grammars serve a useful purpose by providing key phrases for presentation control instructions that distinguish normal speech. In a discussion of a word processing document, for example, references to pages and paragraphs may abound, and using a distinctive phrase to invoke presentation control instructions on pages and paragraphs reduces the risk of confusion on the part of a voice response server and a presentation session.

The profile class (126) also includes a string array storing user classifications (210). Examples of user classifications (210) include any supported data codes describing users, including, for example “company=IBM,” “department=marketing,” “technical level=3,” “security level=2,” and others as will occur to those of skill in the art.

FIG. 2 includes a presentation session class (128) whose objects represent presentation sessions. A presentation session represents an aggregation of presentation documents for presentation usually at a set date and time, for a defined set of users including a presenter in charge. The presentation session class (128) includes a presentation identifier code (212), a presenter identification (214), a list of participants (216). The presentation session class (128) also includes a schedule date and time (218) when a presentation is to be presented, a URI array identifying presentation documents (220) requested by a presenter for a presentation session, a URI array (222) identifying presentation documents that have been filtered according to presentation attributes or user classifications. The presentation session class (128) also includes a member method named mergeGrammars( ) (224) that is programmed to read presentation grammars from presentation documents and store them in a VRS grammar on a voice response server for use in parsing key phrases spoken by a presenter and other users into presentation control instructions.

Agent (110) includes software modules for structuring a presentation document according to content type (114) and for classifying presentation document content according to presentation attributes (116).

FIG. 2 includes an exemplary agent class (110) whose objects are used in content servers to create presentation documents. Agent class (110) includes an array of references to content type plug-ins (114) that are used to create presentation grammars for presentation documents according to content type. FIG. 2 also shows a content type plug-in class (114) with a member method named createPresentationGrammar( ) (232) which in this example is programmed to create presentation grammars for presentation documents according to content type. Agent class (110) also includes an array of references to classification plug-ins (116) that are used to classify presentation document content according to presentation attributes (116). FIG. 2 also shows a classification plug-in class (116) with a member method named classifyDocument( ) (234) which in this example is programmed to classify presentation document content according to presentation attributes.

Agent class (110) also includes a member method named createStructuedDocument( ) (230) which is programmed to convert an original document into a structured document by inserting structural element identifiers. Examples of structural element identifiers include <page>, <paragraph>, <row>, <column>, <cell>, <slide>, <jpeg>, <title>, <heading>, <subheading>, and so on, as will occur to those of skill in the art. These examples of structural elements identifiers are expressed as markup tags such as would be used, for example, in a markup language such as HTML (“HyperText Markup Language”) or XML (“eXtensible Markup Language”), although this is not a limitation of the invention. In fact, it is well within the scope of the present invention to implement structural element identifiers with binary codes, Unicode identifiers, or by use of other structure identifiers as will occur to those of skill in the art.

FIG. 3 sets forth a data flow diagram illustrating a method for creating a presentation document (314) that includes creating (304), in dependence upon an original document (302), a structured document (306) comprising one or more structural elements (402). In the method of FIG. 3, creating (304) a structured document (306) is carried out by inserting (320) in the structured document (306) structural element identifiers (322) for the structural elements (402). An alternative method of creating a structured document, also shown in FIG. 3, is carried out by converting (326) existing structural element identifiers (324) from the original document (302) to structural element identifiers (322) for the structural elements (402) of the structured document (306). The method of FIG. 3 also includes creating (310) a presentation grammar (312) for the structured document (306). In the example of FIG. 3, the presentation grammar (312) for the structured document (306) includes grammar elements (316) each of which includes a structural element identifier (318) for at least one structural element (402) of the structured document (306).

FIG. 4 sets forth a data flow diagram illustrating an exemplary method of creating a presentation grammar (312) for a structured document (306) that includes identifying (404) the content type (410) of the original document (302). Identifying the content type may be carried out, for example, by identifying the content type in dependence upon a filename extension (303) in the filename of an original document. Examples of filename extension identifying content type include ‘pdf’ for Adobe's Portable Document Format, ‘xls’ for a Microsoft Excel™ spreadsheet, ‘doc’ for a word processing document, ‘xml’ for an XML document, and so on, as will occur to those of skill in the art. Alternatively, identifying the content type may be carried out by identifying the content type in dependence upon document header elements in an original document (302). The following is an example of an HTML header identifying an original document having content type HTML version 4.01:

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01//EN” “http://www.w3.org/TR/html4/strict.dtd”>

The method of FIG. 4 includes selecting (406), in dependence upon the content type (410), a full presentation grammar (308) from among a multiplicity of full presentation grammars (412). A full presentation grammar may be implemented, for example, as shown in FIG. 5. A multiplicity of full presentation grammars may be implemented in a data structure similar to the one shown in FIG. 5 by adding a content type column. FIG. 5 sets forth an exemplary data structure (308) in which a full grammar may be implemented according to embodiments of the present invention. The full grammar of FIG. 5 includes several grammar elements (502-514) for a content type. In this example, the content type is taken as a word processing document having structural elements that include pages, paragraphs, bullets, titles, subtitles, and so on, and the data structure includes a column for an identifier (318) of a structural element, a column for a key phrase (516) for formulating a presentation control instruction for invoking a presentation action, and a column for a presentation action identifier (518) representing a presentation action. The exemplary data structure of FIG. 5 also includes a column for a data indication whether a presentation control instruction requires a parameter. The exemplary grammar entries for presentation action identifiers PgDn (502), PgUp (504), nextParagraph (508), and prevBullet (512) have parameter (520) values of ‘null,’ signifying that a voice response server parsing their key phrases into presentation control instructions is not to parse a parameter for a presentation control instruction. The exemplary grammar entries for presentation action identifiers goToPage (506), nextHeading (510), and goToSubtitle (514), however, have parameter (520) values of ‘integer’ and ‘string,’ signifying that a voice response server parsing their key phrases into presentation control instructions is to seek to parse for each of them respectively an integer parameter, a string parameter, and a string parameter.

The method of FIG. 4 includes filtering (408) the full presentation grammar (308) into a presentation grammar (312) for the structured document (306) in dependence upon the structural elements (402) of the structured document (306). Filtering (408) the full presentation grammar (308) may be carried out by writing (414) from the full presentation grammar (308) to the presentation grammar (312) for the structured document (306) each grammar element (316) having a structural element identifier (318) of a structural element (402) that occurs in the structured document (306). Using the exemplary full grammar of FIG. 5, for example, to create a presentation grammar for a structured document having structural elements including pages, paragraphs, headings, and subtitles but no bullet points identified in it as structural elements, filtering (408 on FIG. 4) the full presentation grammar (308) by writing (414) to the presentation grammar (312) grammar elements (502-510) plus grammar element (514) but excluding grammar element (512).

Methods of creating presentation documents are further explained with an exemplary use case. Consider the following example of a structured document:

<document>   <page id=“1”>     <p id=“1”>a paragraph</p>     <p id=“2”>another paragraph</p>     <image id=“1”>a graphic image</image>   </page>   <page id=“2”>     <p id=“3”>a paragraph</p>     <p id=“4”>another paragraph</p>     <image id=“2”>another graphic image</image>   </page> </document>

And assume that this exemplary structured document is associated in a presentation document with the following presentation grammar:

TABLE 1 Presentation Grammar Presentation Structural Action Element Key Phrase Identifier Identifier Parameter page down PgDn <page> null page up PgUp <page> null go to page goToPage <page> integer next paragraph nextParagraph <p> null go to paragraph goToParagraph <p> integer next image nextImage <image> null go to image goToImage <image> integer

This example is discussed with reference to the exemplary system architecture of FIG. 1. In this example, then, when a presentation session (128) displays the first page of the structured document and a user (124) speaks the words “page down,” a voice response server (104), having this presentation grammar as part of its VRS grammar (105), parses the speech into a presentation control instruction having a presentation control identifier named “PgDn” and communicates the presentation control instruction through a presentation interface (132) to the presentation session in presentation server (102) which then displays the next page, in this example, page 2 of the example structured document. Similarly, when the first page of the structured document is on display, a user's speaking the words “go to paragraph 4” results in the presentation session's changing the display to show paragraph 4 on the second page of the document. And, when the first page is on display for the users participating in the presentation and a user speaks the words “next image,” the presentation session changes the display to show image 2 on the second page of the document.

Classifying Structure Elements in a Presentation Document

FIG. 6 is a data flow diagram illustrating a further method for creating a presentation document (314). The method of FIG. 6 includes creating (304), in dependence upon an original document (302), a structured document (306) comprising one or more structural elements (402), as explained in detail above. The method of FIG. 6 also includes classifying (350) a structural element (402) of the structured document (306) according to a presentation attribute (352). FIG. 7 is a data flow diagram illustrating an exemplary method for classifying a structural element that includes identifying (702) a presentation attribute (352) for the structural element (402); identifying (704) a classification identifier (708) in dependence upon the presentation attribute (352); and inserting (706) the classification identifier (708) in association with the structural element (402) in the structured document (306). The method of FIG. 6 also includes creating (310) a presentation grammar (312) for the structured document (306), wherein the presentation grammar (312) for the structured document (306) includes grammar elements (316) each of which includes an identifier (318) for at least one structural element (402) of the structured document (306).

FIG. 8 sets forth a data flow diagram illustrating an exemplary method for classifying a structural element in a structured document in which identifying (702) a presentation attribute (352) for the structural element (402) includes selecting (710) a presentation attribute (352) from a list (712) of supported presentation attributes (352). The presentation attribute list (712) of FIG. 8 includes two columns, one column for presentation attributes (352) and another column for associated classification identifiers (708). In the method of FIG. 8, identifying (704) a classification identifier (708) is carried out by identifying a classification identifier (708) associated with the presentation attribute (352) on the list (712). In the method of FIG. 8, inserting (706) the classification identifier (708) includes manually editing (713) the structured document (306) to insert classification identifiers in appropriate locations to classify structural elements in a structured document. For example, a paragraph to be viewed only by members of the marketing department may be classified by tagging the paragraph with <mkt> </mkt>.

FIG. 9 sets forth a data flow diagram illustrating a further exemplary method for classifying a structural element in a structured document in which identifying (702) a presentation attribute (352) for the structural element (402) includes selecting (710) a presentation attribute (352) from a list (712) of supported presentation attributes (352), the presentation attribute (352) having an associated classification identifier (708). In the method of FIG. 9, identifying (704) a classification identifier (708) includes inserting (716) the classification identifier (708) in a data structure (717) in association with a structural element identifier (322) for the structural element (402). In the method of FIG. 9, inserting (706) the classification identifier (708) in the structured document (306) includes reading (714) the classification identifier (708) from the data structure (717) in dependence upon the structural element identifier (322).

FIG. 10 sets forth a data flow diagram illustrating another exemplary method for classifying a structural element in a structured document that includes providing a list (712) of supported presentation attributes (352) including at least one keyword (802) and at least one indication of structural insertion scope (804) for each presentation attribute (352). In the method of FIG. 10, identifying (702) a presentation attribute (352) for the structural element (402) includes selecting (710) a presentation attribute (352) from the list (712) in dependence upon a keyword (806) from the structured document (306). In the method of FIG. 10, identifying (704) a classification identifier (708) is carried out by identifying a classification identifier (708) associated with the presentation attribute (352) on the list (712). In the method of FIG. 10, inserting (706) the classification identifier (708) is carried out by inserting the classification identifier (708) in the structured document (306) according to a structural insertion scope (804) for the selected presentation attribute (352).

FIG. 11 sets forth a data flow diagram illustrating a further exemplary method for classifying a structural element in a structured document that includes providing a list (712) of supported presentation attributes (352) including at least one data pattern (810) and at least one indication of structural insertion scope (804) for each presentation attribute (352). In the method of FIG. 11, identifying (702) a presentation attribute (352) for the structural element (402) includes selecting (814) a presentation attribute (352) from the list (712) in dependence upon a data pattern (812) from the structured document (306). In the method of FIG. 11, identifying (704) a classification identifier (708) is carried out by identifying a classification identifier (708) associated with the presentation attribute (352) on the list (712). In the method of FIG. 11, inserting (706) the classification identifier (708) is carried out by inserting the classification identifier (708) in the structured document (306) according to a structural insertion scope (804) for the selected presentation attribute (352).

Methods of creating presentation documents are further explained with an exemplary use case. Consider the following example of a structured document:

<document>   <page id=“1”>     <p id=“1”>       a paragraph on an introductory subject     </p>   </page>   <page id=“2”>     <p id=“2”>       a paragraph on a particular subject     </p>     <tech level=“2”>     <p id=“2”>       a more technical paragraph on the same subject     </p>     </tech>     <security level=“2”>     <p id=“2”>       a more secret paragraph on the same subject     </p>     </security>     <dept id=“marketing”>     <p id=“2”>       a paragraph on the same subject with added detail       regarding marketing     </p>     </dept>     <company id=“IBM”>     <p id=“2”>       a paragraph on the same subject with added detail       pertinent to a user’s company     </p>     </company>     <p id=“3”>       a paragraph on a further subject     </p>     ... ... ...   </page>   <page id=“3”>     ... ... ...   </page>   ... ... ... </document>

This example is discussed with reference to the exemplary system architecture of FIG. 1, assuming that this exemplary structured document is associated in a presentation document with a presentation grammar that includes presentation action identifiers for paragraphs and pages uploaded to a VRS grammar (105) in a voice response server (104). In this example, then, when a presentation session (128) is displaying the first page of the structured document and a user (124) speaks the words “next page,” a voice response server (104) parses the speech into a presentation control instruction with a presentation action identifier named “PgDn” and communicates the presentation control instruction through a presentation interface (132) to the presentation session which then displays the next page, in this example, page 2 of the example structured document. Assume that there are five users (124) registered as participants with the presentation session (128), and note that there are five different versions of paragraph 2 on page two of the structured document.

In this example, a first version of paragraph 2 bears a structural identifier <p></p> identifying it as a paragraph, but this first version of paragraph 2 bears no classification identifier. In this example, presentation session (128) is programmed to display this unclassified version of paragraph 2 to users having either the lowest technical classifications, the lowest security classifications, or no particular technical or security classifications at all. Moreover, in an example, where there were only one version of paragraph 2, all users would be presented with that one version.

In this example, a second version of paragraph 2 is classified with a classification identifier <tech level=“2”>. In this example, presentation session (128) is programmed to display this second version of paragraph 2 to users having user classification indicating technical level 2. That is, when a user having technical level 2 in the user's profile classifications (210 on FIG. 2) is registered with the presentation session, upon being directed to display paragraph 2, rather than displaying an unclassified version of paragraph 2, the presentation session displays the second version of paragraph 2 classified <tech level=“2”> to such a user.

Similarly, a user having a user profile classification representing a heightened security authorization, security level 2, is shown the version of paragraph 2 classified by the classification identifier <security level=“2”>. A user having a user profile classification identifying the user as a member of the marketing department is shown the version of paragraph 2 classified by the classification identifier <dept id=“marketing”>. A user having a user profile classification identifying the user as an employee of IBM is shown the version of paragraph 2 classified by the classification identifier <company id=“IBM”>.

For purposes of clarity of explanation, the structural elements in this example are shown with only one classification per element. Persons of skill in the art will recognize, however, that it is well within the scope of the present invention for a structural element of a structured document to be classified with any number of classification identifiers.

Creating a Voice Response Grammar from a Presentation Grammar

FIG. 12 sets forth a data flow diagram illustrating a method for creating a voice response grammar in a voice response server including identifying (354) presentation documents (118) for a presentation. In the method of FIG. 12, each presentation document has a presentation grammar (120), and the method includes storing (358) each presentation grammar (120) in a voice response grammar (105) on a voice response server (104). Presentation grammars and voice response grammars may be structured like the full grammars illustrated in FIG. 5 with grammar elements (502-514) for a content type (410). In the exemplary grammar structure of FIG. 5, the content type is taken as a word processing document having structural elements that include pages, paragraphs, bullets, titles, subtitles, and so on, and the data structure includes a column for an identifier (318) of a structural element, a column for a key phrase (516) for formulating a presentation control instruction to invoke a presentation action, and a column for a presentation action identifier (518) representing a presentation action.

In the method of FIG. 12, identifying (354) presentation documents (118) for a presentation includes creating (360) a data structure (128) representing a presentation and listing (362) at least one presentation document (118) in the data structure (128) representing a presentation. A data structure representing a presentation may be implemented as an instance of a presentation session class as shown at reference (128) on FIG. 2. In the method of FIG. 12, listing (362) the at least one presentation document (118) includes storing (366) a location (364) of the presentation document (118) in the data structure (128) representing a presentation. In the exemplary structure of FIG. 2, storing a location of a presentation document may be implemented by storing presentation document locations in the form of URIs in an array of URIs (220). In the method of FIG. 12, storing (358) each presentation grammar (120) includes retrieving (368) a presentation grammar (120) of the presentation document (118) in dependence upon the location (364) of the presentation document (118).

In one exemplary embodiment of the method of FIG. 12, the presentation document (118) is implemented as a file in a file system on a content server (106) and the file has a location (364) identified by a pathname. In such an embodiment, storing (366) a location (364) of the presentation document (118) in the data structure (128) representing a presentation includes storing the pathname and a network location of the content server. An example of storing a pathname and a network location is storing a URI for the document in a URI array such as that illustrated at reference (220) on FIG. 2. Such a URI may have the form:

http://www.someContentServer.com/presentationDocuments/myDoc.doc

where www.someContentServer.com is a domain name for a web server that maps to a network address such as an Internet Protocol address, for example, of a computer where a web server is located. A ‘web server’ is a server that supports data communications according the HyperText Transport Protocol (‘HTTP’). The portion of the URI after the domain name, “presentationDocuments/myDoc.doc,” is a pathname for a document on the computer on which the web server is located. In such an embodiment, retrieving (368) a presentation grammar includes retrieving the presentation document from the content server (106) in dependence upon the pathname and extracting the grammar from the presentation document. In an example where the presentation document is located according to a URI as described above and the content server is implemented with a web server, retrieving the presentation document from the content server may be carried out by parsing the URI into an HTTP GET message:

GET/presentationDocuments/myDoc.doc HTTP/1.1

and transmitting the GET message to the content server at www.ibmContentServer.com.

In this example, the content server returns the presentation document as URI encoded data in an HTTP RESPONSE message. In an example where the returned presentation document has this form:

<presentationDocument>   <presentationGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>         page down       </keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >   </presentationGrammar>   <structuredDocument>     <page id=“1”>       <p id=“1”> a paragraph </p>       <p id=“2”> another paragraph </p>     </page>     <page id=“2”> some text </page>   </structuredDocument> </presentationDocument>, extracting the grammar from the presentation document may be carried out by extracting the portion of the presentation document identified by the tags:

<presentationGrammar> </presentationGrammar>

In another exemplary embodiment of the method of FIG. 12, the presentation document (118) is implemented as an instance of an object oriented class on a content server (106). In this example, the presentation document has a presentation document name, and the presentation grammar comprises a member data element of the instance. In such an embodiment, storing (366) a location (364) of the presentation document (118) in the data structure (128) representing a presentation includes storing the presentation document name and a network location of the content server.

An example of storing a pathname and a network location is storing a URI for the document in a URI array such as that illustrated at reference (220) on FIG. 2. Such a URI may have the form:

http://www.ibmContentServer.com/servlets/ getPresentationGrammar?presDoc=myDoc.doc where www.someContentServer.com is a domain name for a web server. The portion of the URI after the domain name but before the question mark, “servlets/getPresentationGrammar,” is a pathname for server-side functionality for retrieving a presentation document. The server-side functionality could be a CGI (Common Gateway Interface (‘CGI’) script or other server-side functionality as will occur to those of skill in the art, but in this example the server-side functionality is taken as a Java servlet identified by its name, “getPresentationGrammar.” The remainder of the URI is query data encoded as a name-value pair identifying the name of a presentation document, “myDoc.doc,” from which a presentation grammar is to be extracted by the servlet.

In such an exemplary embodiment, retrieving (368) a presentation grammar is carried out by requesting the presentation grammar (120) from the content server (106), including communicating the presentation document name as a request parameter; and receiving the presentation grammar (120) in response from the content server (106). In an example where the presentation document is located according to a URI as described above and the content server is implemented with a web server, requesting the presentation grammar (120) from the content server (106), including communicating the presentation document name as a request parameter, may be carried out by parsing the URI into an HTTP GET message:

GET/servlets/getPresentationGrammar?presDoc=myDoc.doc HTTP/1.1

and transmitting the GET message to the content server at www.ibmContentServer.com.

In another exemplary embodiment of the method of FIG. 12, the presentation document (118) includes a record in a table in a database on a content server (106). In this example, the presentation document has a presentation document identifier, and the presentation grammar comprises a field in the record. In such an embodiment, storing (366) a location (364) of the presentation document (118) in the data structure (128) representing a presentation includes storing the presentation document identifier and a network location of the content server. In a database table in which each record represents a presentation document, for example, the presentation document identifier may be implemented as a single field unique key such as a serial number for a record, as a presentation document name, or as any functional identifier as will occur to those of skill in the art. In the continuing discussion of this example, the presentation document identifier is taken as a presentation document name.

An example of storing a presentation document identifier and a network location is storing a URI for the document in a URI array such as that illustrated at reference (220) on FIG. 2. Such a URI may have the form:

http://www.ibmContentServer.com/ cgi-bin/getPresentationGrammar?presDoc=myDoc.doc where www.someContentServer.com is a domain name for a web server. The portion of the URI after the domain name but before the question mark, “/cgi-bin/getPresentationGrammar,”is a pathname for server-side functionality for retrieving a presentation document. The server-side functionality could be a Java servlet or other server-side functionality as will occur to those of skill in the art, but in this example the server-side functionality is taken as a CGI script named “getPresentationGrammar.” The remainder of the URI is query data encoded as a name-value pair identifying the name of a presentation document, “myDoc.doc,” from which a presentation grammar is to be extracted by the CGI script.

In such an exemplary embodiment, retrieving (368) a presentation grammar is carried out by requesting the presentation grammar (120) from the content server (106), including communicating the presentation document name as a request parameter; and receiving the presentation grammar (120) in response from the content server (106). In an example where the presentation document is located according to a URI as described above and the content server is implemented with a web server, requesting the presentation grammar (120) from the content server (106), including communicating the presentation document name as a request parameter, may be carried out by parsing the URI into an HTTP GET message:

GET/cgi-bin/getPresentationGrammar?presDoc=myDoc.doc HTTP/1.1

and transmitting the GET message to the content server at www.ibmContentServer.com.

Creating a Voice Response Grammar from a User Grammar

FIG. 13 sets forth a data flow diagram illustrating a method for creating a voice response grammar in a voice response server including identifying (372) a user (374) for a presentation where the user has a user grammar (208) and the user grammar includes one or more user grammar elements (378). The method of FIG. 13 also includes storing (376) a multiplicity of user grammar elements (378) for the user in a voice response grammar (105) on a voice response server (104). A user grammar is a data structure that includes a set of key phrases specific to a user that are used to formulate presentation control instructions for invoking presentation actions on presentation servers. For a presentation control instruction that invokes a presentation action instructing a presentation session to ‘page down,’ for example, an individual user may chose to associate with that presentation control instruction the key phrase “rock and roll” or “boogie on down” or any other key phrase favored by a user as will occur to those of skill in the art. Although these particular example are somewhat fanciful, in fact, user grammars serve a useful purpose by providing key phrases for presentation actions that distinguish normal speech. User grammars and voice response grammars may be structured like the full grammars illustrated in FIG. 5 with grammar elements (502-514) for a content type (410).

In the method of FIG. 13, identifying (372) a user for a presentation includes creating (360) a data structure (128) representing a presentation and listing (380) in the data structure (128, 374) at least one user identification (204). A data structure representing a presentation may be implemented as an instance of a presentation session class as shown at reference (128) on FIG. 2. In the method of FIG. 13, listing (380) in the data structure (128, 374) at least one user identification (204) includes creating a list of user names of the users that are registered with the presentation session. That is, a list of users currently participating in the presentation.

In the example of FIG. 13, the user grammar (208) includes a multiplicity of user grammar elements (378) for a content type (370). In this example, each grammar element includes an identifier of a structural element, a key phrase for invoking a presentation action, and an action identifier representing the presentation action, as shown for example in the depiction of an exemplary full grammar at references (318), (518), and (516) on FIG. 5.

The method of FIG. 13 includes identifying (382) presentation documents (118) for the presentation. In this example, each presentation document (118) having a content type (370), and selecting (384) user grammar elements (386) according to the content type (370) of the identified presentation documents (356). In the example of FIG. 13, selecting (384) user grammar elements (386) according to the content type (370) of the identified presentation documents (356) includes comparing the elements of the user grammar with each presentation document in the presentation session and extracting each element of the grammar having the same content type as a presentation document in the presentation session. In the method of FIG. 13, storing (376) a multiplicity of user grammar elements for the user in a voice response grammar on a voice response server is carried out by storing the selected user grammar elements (386) in the voice response grammar (105).

FIG. 14 is a data flow diagram illustrating an alternative exemplary method for creating a voice response grammar in a voice response server. The method of FIG. 14 includes identifying (388) presentation documents (118) for the presentation. The presentation documents (118) in this example include structured documents (122) having structural element identifiers (322). In the example of FIG. 14, the identified presentation documents are included in a presentation document list (356) in the presentation session.

The user grammar (208) in this example includes a multiplicity of user grammar elements (378), and the method includes selecting (390) user grammar elements (378) in dependence upon the structural element identifiers (322). In this example, selecting (390) user grammar elements (378) in dependence upon the structural element identifiers (322) is carried out by comparing the elements of the user grammar with each structured document of each presentation document in the presentation session and extracting each user grammar element having a structural element identifier for a structural element that occurs in a structured document of a presentation document in the presentation session. In the method of FIG. 14, storing (376) a multiplicity of user grammar elements for the user in a voice response grammar on a voice response server includes storing the selected user grammar elements (386) in the voice response grammar (105).

FIG. 15 is a data flow diagram illustrating another alternative exemplary method for creating a voice response grammar in a voice response server. The method of FIG. 15 includes identifying (398) presentation documents (118) for the presentation. Each presentation document (118) has a presentation grammar (120) including presentation action identifiers (518).

In the example of FIG. 15, the user grammar (208) includes a multiplicity of user grammar elements (378), and the method includes selecting (396) user grammar elements (378) in dependence upon the presentation action identifiers (518). In this example, selecting (396) user grammar elements (378) in dependence upon the presentation action identifiers (518) is carried out by comparing the elements of the user grammar with each presentation grammar of each presentation document of the presentation session and extracting from the user grammar each element having a presentation action identifier that occurs in a presentation grammar of the presentation document. In the method of FIG. 15, storing (376) a multiplicity of user grammar elements for the user in a voice response grammar on a voice response server includes storing the selected user grammar elements (386) in the voice response grammar (105).

Creating a Session Document from a Presentation Document

FIG. 16 sets forth a data flow diagram illustrating an exemplary method for creating a session document (266) from a presentation document (314). A session document is a repository for filtered content, presentation content that is filtered according to attributes of an audience for a presentation, an audience that presents a range of affiliations, technical abilities, security authorizations, and other attributes as will occur to those of skill in the art. The purpose of a session document is to provide a repository for reducing the volume of data for a presentation with respect to unfiltered presentation documents. A session document is a document derived from a presentation document targeted for the participants of a presentation. More particularly, a session document is a data structure that includes a session grammar derived from a presentation grammar in a presentation document and a session structured document derived from a structured document in a presentation document.

The method of FIG. 16 includes identifying (250) a presentation document (314) for a presentation. The presentation document (314) includes a presentation grammar (312) and a structured document (306) having structural elements (402) classified with classification identifiers (708). Identifying (250) a presentation document (314) typically includes inserting in a list (220) a location for the presentation document (314). The location of a presentation document may be represented by a URI, and a list of locations identifying presentation documents may be implemented as an array of URIs as exemplified by the requested content list (220) in the exemplary presentation session class (128) on FIG. 2.

The method of FIG. 16 includes identifying (252) a user participant (204) for the presentation. In the method of FIG. 16, the user has a user profile (126) that includes user classifications (210) each of which describes some attribute of a user, such as, for example, company affiliation, department membership, technical ability, security authorization level, and so on, for any attribute of a user as may occur to those of skill in the art. Identifying (252) a user (204) typically includes inserting in a list (374) a user identification (204) identifying a user in a presentation participant list (374). In the example of FIG. 16, a user identification is implemented as a user name (204) in a user profile (126).

The method of FIG. 16 includes filtering (254) the structured document (306) in dependence upon the user classifications (210) and the classification identifiers (708). In the method of FIG. 16, filtering (254) the structured document (306) is carried out by extracting (258), from the structured document (306), structural elements (402) having classification identifiers (708) corresponding to the user classifications (210), and writing (260) the extracted structural elements (402) into a session structured document (256) in the session document (266). The method of FIG. 16 also includes filtering (262) the presentation grammar (312), in dependence upon the extracted structural elements (402), into a session grammar (258) in the session document (266). The method of FIG. 16 includes storing (264) the location of the session document (266) in a session document list (222).

For further explanation, consider an example of creating a session document that begins with a presentation document having the following contents:

<presentationDocument>   <presentationGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>page down</keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >     <grammarElement>       <contentType id=“WP”>       <keyPhrase>next bullet</keyPhrase>       <presentationAction id=“NextBullet”>       <structuralElementIdentifier id=“bullet”>     </grammarElement >   </presentationGrammar>   <structuredDocument>     <page id=“1”>       <p id=“1”>a paragraph on some subject</p>     </page>     <page id=“2”>       <p id=“2”>a paragraph on a particular subject</p>       <tech level=“2”>       <p id=“2”>a more technical paragraph, same       subject</p>       </tech>       <security level=“2”>       <p id=“2”>a more secret paragraph, same subject</p>       </security>       <dept id=“marketing”>       <p id=“2”>a paragraph, same subject, with added detail         regarding marketing         <bullet id =“1”>some bullet text</bullet>         <bullet id =“1”>some other bullet text</bullet>         <bullet id =“1”>still more bullet text</bullet>       </p>       </dept>       <company id=“IBM”>       <p id=“2”>a paragraph, same subject with added detail       pertinent to a user's company</p>       </company>       <p id=“3”>a paragraph on some other subject</p>       ... ... ...     </page>   </structuredDocument> </presentationDocument>

In this example, an audience of users identified for a presentation include users having in their user profiles user classifications indicating technical level ‘2’ and membership in IBM. None of the registered users have security authorizations and none of them are from the marketing department. Filtering this exemplary presentation document, extracting structural elements with classification identifiers corresponding to the user classifications, writing those structural elements to a session document, and filtering the presentation grammar in dependence upon the extracted structural elements, results in the following exemplary session document:

<sessionDocument>   <sessionGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>page down</keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >   </sessionGrammar>   <sessionStructuredDocument>     <page id=“1”>       <p id=“1”> a paragraph </p>       <p id=“2”> another paragraph </p>     </page>   <page id=“2”>     <p id=“2”>a paragraph on a particular subject</p>     <tech level=“2”>     <p id=“2”>a more technical paragraph, same subject</p>     </tech>     <company id=“IBM”>     <p id=“2”>a paragraph, same subject with added detail       pertinent to a user's company</p>     </company>     <p id=“3”>a paragraph on some other subject</p>     ... ... ...   </page>   </sessionStructuredDocument> </sessionDocument>

In the resulting session document, the structural element identified as page 2 now excludes versions for security level 2 and for marketing, because none of the users listed for the presentation are in the marketing department or have security authorizations of level 2. In addition, the session grammar excludes a grammar element for bullets because, in the session document above, the only structural element having bullets was the version of paragraph 2 for the marketing department. Excluding the bullets as structural elements in the session structured document means that there is no need to have grammar elements for them in the session grammar. Reducing the number of grammar elements in the session grammar reduces the number of grammar elements in the voice response grammar, thereby increasing the efficiency and accuracy of the voice response server and the overall presentation system.

Amending a Session Document During a Presentation

FIG. 17 sets forth a data flow diagram illustrating an exemplary method for amending a session document (266) during a presentation. The session document (266) includes a session structured document (256), and the method of FIG. 17 includes providing (268) user profiles (126) representing users capable of participating in presentations. In typical embodiments, user profiles for all the users capable of participating in presentations are stored in a database accessible to the presentation session. In the example of FIG. 17, each user profile (126) includes user classifications (210) for a user.

The method of FIG. 17 also includes providing (270) a presentation document (314) that includes a structured document (306) having structural elements (402) classified with classification identifiers (708). In the example of FIG. 17, the locations of the presentation documents from which the session documents for a particular presentation were created are stored in a list such as the requested content list (220) of FIG. 17.

The method of FIG. 17 includes identifying (274) a user profile event (272) for a user during the presentation. A user profile event is an event that results in adding a user classification to the set of user classifications for a presentation. The set of user classifications for a presentation is the set of all user classifications for all users that have been identified as users for a presentation. A user profile event may be represented as a data structure (272) that includes a user identification (205) for a particular user.

A user profile event (272) may be generated by adding a user to the presentation, where the added user has a new user classification for the presentation. That is, one example of a user profile event (272) is adding to a presentation a user whose user classifications include at least one user classification having no corresponding classification identifier in any structural element in the session structured document. In such an example, at least one of the added user's user classifications is currently not part of any user profile of any of the other users identified for the presentation.

A user profile event (272) also may be generated, for a further example, by changing a user classification (210) in a user profile (126) of a user who is participating in the presentation, where the changed user classification includes a new user classification for the presentation. That is, one example of a user profile event (272) is editing a user's profile during a presentation so that the user's user profile now includes a user classification having no corresponding classification identifier in any structural element in the session structured document. In such an example, the new user classification is currently not part of any user profile of any of the other users identified for the presentation.

The method of FIG. 17 includes adding (276) to the session structured document (256) at least one structural element (402) from the presentation document (314), the added structural element (402) having a classification identifier (708) that corresponds to a user classification (210) of the user. In the examples just mentioned, regarding adding a new user to a presentation or a new user classification to a profile, adding (276) to the session structured document (256) a structural element (402) from the presentation document (314), the added structural element (402) having a classification identifier (708) that corresponds to a user classification (210) of the user, means that the new structural element is one that no other user identified for the presentation was entitled to view. Because adding a structural element may mean adding a structural element of a kind not otherwise represented in the session structured document, the method of FIG. 17 advantageously also includes adding (278) a grammar element (316) to the session grammar (258) in dependence upon the added structural element (402).

For further explanation, consider the following example of amending a session document (266) during a presentation. In this example, a session document is used for a presentation having users whose user profiles include user classifications of technical level ‘2’ and membership in IBM:

<sessionDocument>   <sessionGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>page down</keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >   </sessionGrammar>   <sessionStructuredDocument>     <page id=“1”>       <p id=“1”> a paragraph </p>       <p id=“2”> another paragraph </p>     </page>   <page id=“2”>     <p id=“2”>a paragraph on a particular subject</p>     <tech level=“2”>     <p id=“2”>a more technical paragraph, same subject</p>     </tech>     <company id=“IBM”>     <p id=“2”>a paragraph, same subject with added detail       pertinent to a user's company</p>     </company>     <p id=“3”>a paragraph on some other subject</p>     ... ... ...   </page>   </sessionStructuredDocument> </sessionDocument>

This session document in this example was created from the following presentation document:

<presentationDocument>   <presentationGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>page down</keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >     <grammarElement>       <contentType id=“WP”>       <keyPhrase>next bullet</keyPhrase>       <presentationAction id=“NextBullet”>       <structuralElementIdentifier id=“bullet”>     </grammarElement >   </presentationGrammar>   <structuredDocument>     <page id=“1”>       <p id=“1”>a paragraph on some subject</p>     </page>     <page id=“2”>       <p id=“2”>a paragraph on a particular subject</p>       <tech level=“2”>       <p id=“2”>a more technical paragraph, same       subject</p>       </tech>       <security level=“2”>       <p id=“2”>a more secret paragraph, same subject</p>       </security>       <dept id=“marketing”>       <p id=“2”>a paragraph, same subject, with added detail         regarding marketing         <bullet id =“1”>some bullet text</bullet>         <bullet id =“1”>some other bullet text</bullet>         <bullet id =“1”>still more bullet text</bullet>       </p>       </dept>       <company id=“IBM”>       <p id=“2”>a paragraph, same subject with added detail       pertinent to a user's company</p>       </company>       <p id=“3”>a paragraph on some other subject</p>       ... ... ...     </page>   </structuredDocument> </presentationDocument>

The session document in this example contains no structural elements classified for users from the marketing department. After beginning the presentation a user from the marketing department joins the presentation. The user's joining the presentation is represented by adding the user's user identification to a list of users identified for the presentation. Adding the user ID to the list identifies (274) a user profile event (272) which is represented by a data structure that includes the user's user identification (205). Amending the session document proceeds by adding (276) to a session structured document (256) one or more structural elements (402) from a structured document in the presentation document from which the session structured document was created. Adding (276) to the session structured document (256) at least one structural element (402) from the presentation document (314) is carried out by adding a structural element (402) having a classification identifier (708) that corresponds to a user classification (210) of the user. User classifications of the user are read from the user profiles (126) using the user identification (205) provided to the adding process (276) by the user profile event (272). In this example, adding a structural element to the session structured documents is carried out by adding the following paragraph from the structured document of the presentation document set forth above:

<dept id=“marketing”> <p id=“2”>a paragraph, same subject, with added detail regarding marketing   <bullet id =“1”>some bullet text</bullet>   <bullet id =“1”>some other bullet text</bullet>   <bullet id =“1”>still more bullet text</bullet> </p> </dept>, thereby creating the following amended session document:

<sessionDocument>   <sessionGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>page down</keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >   </sessionGrammar>   <sessionStructuredDocument>     <page id=“1”>       <p id=“1”> a paragraph </p>       <p id=“2”> another paragraph </p>     </page>   <page id=“2”>     <p id=“2”>a paragraph on a particular subject</p>     <tech level=“2”>     <p id=“2”>a more technical paragraph, same subject</p>     </tech>     <company id=“IBM”>     <p id=“2”>a paragraph, same subject with added detail       pertinent to a user's company</p>     </company>     <dept id=“marketing”>     <p id=“2”>a paragraph, same subject, with added detail       regarding marketing       <bullet id =“1”>some bullet text</bullet>       <bullet id =“1”>some other bullet text</bullet>       <bullet id =“1”>still more bullet text</bullet>     </p>     </dept>     <p id=“3”>a paragraph on some other subject</p>     ... ... ...   </page>   </sessionStructuredDocument> </sessionDocument>

Amending the session document also includes adding to the session grammar of the session document a new grammar element from the presentation grammar. There were no bullets in the session structured document before the exemplary user profile event and therefore no grammar elements supporting presentation control instructions for bullets. Adding the marketing paragraph also added bullets, so the method advantageously includes adding grammar elements supporting presentation control instructions for bullets:

<grammarElement>   <contentType id=“WP”>   <keyPhrase>next bullet</keyPhrase>   <presentationAction id=“NextBullet”>   <structuralElementIdentifier id=“bullet”> </grammarElement >, thereby creating the following amended session document:

<sessionDocument>   <sessionGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>page down</keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >     <grammarElement>       <contentType id=“WP”>       <keyPhrase>next bullet</keyPhrase>       <presentationAction id=“NextBullet”>       <structuralElementIdentifier id=“bullet”>     </grammarElement >   </sessionGrammar>   <sessionStructuredDocument>     <page id=“1”>       <p id=“1”> a paragraph </p>       <p id=“2”> another paragraph </p>     </page>   <page id=“2”>     <p id=“2”>a paragraph on a particular subject</p>     <tech level=“2”>     <p id=“2”>a more technical paragraph, same subject</p>     </tech>     <company id=“IBM”>     <p id=“2”>a paragraph, same subject with added detail       pertinent to a user's company</p>     </company>     <dept id=“marketing”>     <p id=“2”>a paragraph, same subject, with added detail       regarding marketing       <bullet id =“1”>some bullet text</bullet>       <bullet id =“1”>some other bullet text</bullet>       <bullet id =“1”>still more bullet text</bullet>     </p>     </dept>     <p id=“3”>a paragraph on some other subject</p>     ... ... ...   </page>   </sessionStructuredDocument> </sessionDocument>

Differential Dynamic Content Delivery

FIG. 18 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery. Differential dynamic content delivery is delivery of the content of a presentation to user participants according to a wide variety of participant interest, company, group, or department membership, technical knowledge, security authorization, and so on, across almost any dimension in which participants may vary. Differential dynamic content delivery is accomplished generally in methods and systems according to embodiments of the present invention by use of structured, classified documents, presentation documents and session documents, each of which includes a grammar and a structured document as described below. Using such documents as a source of presentation content, differential dynamic content delivery is accomplished then by selecting from a structured document classified structural elements for delivery to particular user participants according to the classification identifiers in the document and user classifications from user profiles.

FIG. 18 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery that includes providing (450) a session document (266) for a presentation. In the method of FIG. 18, the session document (266) includes a session grammar (258) and a session structured document (256), and providing (450) a session document (266) for a presentation is carried out by creating a session document from a presentation document as described in detail above in the discussion regarding FIG. 16.

The method of FIG. 18 also includes creating (462) a presentation control instruction (460). A presentation control instruction is an instruction to a presentation server (102) to carry out a particular presentation action such as, for example, ‘display next page,’ ‘display next slide,’ ‘display paragraph 5,’ and so on. More particularly, in differential dynamic content delivery, presentation actions are carried out by presenting to a particular user a version of a particular structural element, such as a paragraph or a slide, according to user classifications such as company name, department name, security authorization, and so on. In the method of FIG. 18, an exemplary presentation control instruction (460) includes a presentation action identifier (518) and one or more optional parameters (520).

In the method of FIG. 18, creating the presentation control instruction is carried out by receiving (464) from a user (124) participating in the presentation a key phrase (516) and optional parameters (520) for invoking a presentation action and parsing (466) the key phrase (516) and parameters (520) against a voice response grammar (105) into a presentation control instruction (460). In this example, receiving (464) a key phrase (516) is carried out by use of a Voice Over Internet Protocol (“VoIP”) link (130) that carries the speech of at least one user (124) from the user's client device to a voice response server (104). A VoIP link is a kind of computer hardware and software that uses an internet protocol network instead of a traditional telephone network as the transmission medium for speech. VoIP is sometimes referred to as ‘IP telephony’ or ‘Voice Over the Internet’ (“VOI”). Examples of user client devices include any computer equipment capable of converting input speech to digital data and transmitting it over the internet protocol to a voice response server, including handheld wireless devices, personal digital assistants, personal computers, laptop computers, and the like.

The method of FIG. 18 also includes receiving (458) a presentation control instruction (460) in a presentation server and selecting (452) from a session structured document (256) a classified structural element (402) in dependence upon user classifications (210) of a user participant (124) in the presentation. In the method of FIG. 18, selecting (452) a classified structural element (402) is carried out by selecting a classified structural element (402) in dependence upon the presentation action identifier (518) and the parameters (520) from the presentation control instruction (460). In the method of FIG. 18, selecting (452) a classified structural element (402) also includes selecting a classified structural element having an associated classification identifier (708) that corresponds to the user classification (210).

For further explanation, consider an example using the following exemplary session document:

<sessionDocument>   <sessionGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>page down</keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >   </sessionGrammar>   <sessionStructuredDocument>     <page id=“1”>       <p id=“1”> a paragraph </p>       <p id=“2”> another paragraph </p>     </page>     <page id=“2”>       <p id=“2”>a paragraph on a particular subject</p>       <tech level=“2”>       <p id=“2”>a more technical paragraph, same         subject</p>       </tech>       <company id=“IBM”>       <p id=“2”>a paragraph, same subject with added detail         pertinent to a user's company</p>       </company>       <p id=“3”>a paragraph on some other subject</p>       ... ... ...     </page>   </sessionStructuredDocument> </sessionDocument>

In this example, assume that a first user participant has in a user profile user classifications indicating that the user is an IBM employee and a second user has user classifications indicating that the user has technical ability level ‘2’. In this example, a presentation server having the above session document installed upon it receives (458) a presentation control instruction (460) to move to the display to the second page of the session structured document. The presentation server then selects (452) from the session structured document (256) for the first user the structural element identified as a version of page two and classified as:

<company id=“IBM”> <p id=“2”>a paragraph, same subject with added detail   pertinent to a user's company</p> </company> and for the second user the structural element identified as a version of page two and classified as:

<tech level=“2”> <p id=“2”>a more technical paragraph, same subject</p> </tech>

The method of FIG. 18 also includes presenting (454) the selected structural element (456) to the user (124). In the method of FIG. 18, presenting (454) the selected structural element (456) to the user may be carried out, for example, by selecting a data communications protocol for the presentation, inserting the selected structural element (without its classification identifiers) in a data structure appropriate to the data communications protocol, and transmitting the data structure to the user according to the data communications protocol. If, for example, the data communications protocol is selected as HTTP, a data structure appropriate to the data communications protocol is an HTML document in an HTTP RESPONSE message. In such an example, presenting (454) the selected structural element (456) to the user may be carried out, for the two exemplary versions of page two selected above, by the following HTTP RESPONSE messages:

HTTP/1.1 200 OK Date:       Content-Type: text/xml Content-Length: 128 <html><body><p id=“2”>a paragraph, same subject with added detail pertinent to a user's company</p> </body></html> and for the second user the structural element identified as a version of page two and classified as:

HTTP/1.1 200 OK Date:       Content-Type: text/xml Content-Length: 103 <html><body><p id=“2”>a more technical paragraph, same subject</p></body></html> respectively, the first sent to the client device of the first user and the second sent to the client device of the second user. Note that in both transmission, the classification identifiers are omitted, <company id=“IBM”> and <tech level=“2”> respectively.

This example of presenting (454) a selected structural element (456) to a user (124) is expressed in terms of HTML and HTTP, a stateless, asynchronous protocol. Many embodiments will statefully hold open a data communications connection, such as a TCP/IP connection, between a presentation server and a user client device. A Stateful Java Enterprise Session Bean™ may be used, for example, to hold open a TCP/IP connection implemented with a Java socket object. Readers of skill in the art will recognize therefore that HTML and HTTP are used for explanation, not for limitation. In fact, any presentation application using any appropriate data communications protocol useful for multi-media presentations may be used to present structural elements to users according to embodiments of the present invention. Such application may be obtained off-the-shelf commercially or they may be specially developed for particular presentations or kinds of presentation. An example of such an application available commercially is Microsoft NetMeeting™. Examples of other data communications protocols useful with various embodiments of the present invention include the Session Initiation Protocol (‘SIP’) specified in the IETF's RFC 2543, the Real Time Streaming Protocol (‘RTSP’) as specified in the IETF's RFC 2326, the Real Time Transport Protocol (‘RTTP’) of RFC 1889, and the World Wide Web Consortium's VoiceXML protocol specified in the 2003 document entitled “Voice Extensible Markup Language (VoiceXML) Version 2.0”.

Differential Dynamic Content Delivery with a Planned Agenda

FIG. 19 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery with a planned agenda. FIG. 19 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery that includes providing (450) a session document (266) for a presentation. In the method of FIG. 19, the session document (266) includes a session grammar (258) and a session structured document (256). The session structured document (256) in this example includes at least one structural element (402) classified with at least one classification identifier (708), although readers will understand that as a practical matter the session structured document (256) typically will have many structural elements (402) classified with many classification identifiers (708). In this example, providing (450) a session document (266) for a presentation is carried out by creating a session document from a presentation document as described in detail above in the discussion regarding FIG. 16.

The method of FIG. 19 also includes establishing (952) a planned agenda (962) for the presentation. For further explanation, FIG. 20 sets forth an table (751) illustrating a planned agenda. Each record in table (751) represents a component of a planned agenda, a presentation plan for a structural element. The planned agenda of FIG. 20 includes a column (750) identifying the structural elements for which duration and sequence are planned. The data values in column (750), “P1-S1, “P1-S2,” P1-S3,” and so on, may represent, for example: Page 1, Section 1; Page 1, Section 2; Page 1, Section 3; and so on, each designating a particular structural element of a session structured document. The particular data values in column (750) are for explanation, not for limitation of the present invention. Many ways of identifying individual structural elements will occur to those of skill in the art, and all such ways are well within the scope of the present invention.

The planned agenda of FIG. 20 includes planned durations (754) for presentation of structural elements and a planned sequence (752) for presentation of structural elements. In the example of FIG. 20, records in table (751) are sorted according to planned sequence (752) of presentation for the structural elements in a planned agenda, and each structural element has a planned duration (754) of presentation of 3.0 minutes.

Again with reference to FIG. 19: The method of FIG. 19 includes receiving (458) a presentation control instruction (460) in a presentation server (102) and selecting (452) from a session structured document (256) a classified structural element (402) in dependence upon user classifications (210 on FIG. 18) of a user participant (980) in the presentation. As discussed above, a presentation control instruction (460) is an instruction to a presentation server (102) to carry out a particular presentation action such as, for example, ‘display next page,’ ‘display next slide,’ ‘display paragraph 5,’ and so on. In the method of FIG. 19, selecting (452) a classified structural element (402) is carried out by selecting a classified structural element (402) in dependence upon the presentation action identifier (518) and one or more parameters (520) from the presentation control instruction (460). In the method of FIG. 19, selecting (452) a classified structural element (402) also includes selecting a classified structural element having an associated classification identifier (708) that corresponds to the user classification (210 on FIG. 18).

The method of FIG. 19 also includes presenting (454) the selected structural element (456) to the user participant (980). In the method of FIG. 19, presenting (454) the selected structural element (456) to the user participant may be carried out, for example, by selecting a data communications protocol for the presentation, inserting the selected structural element (without its classification identifiers) in a data structure appropriate to the data communications protocol, and transmitting the data structure to the user according to the data communications protocol, all as described in more detail above with respect to the method of FIG. 18. As mentioned above, examples of data communications protocols useful for presenting selected structural elements according to embodiments of the present invention include HTTP, SIP, RTSP, RTTP, VoiceXML, and others as will occur to those of skill in the art.

The method of FIG. 19 also includes recording (950), during the presentation, identities (956) of presented structural elements, durations (958) of presentation of presented structural elements, and sequence (960) of presentation of presented structural elements. Recording sequence (960) may be implemented by incrementing and storing an integer, in association with an identification of a selected structural element, whenever presentation server (102) transmits a message in a data communication protocol implementing presentation of a selected structural element to a user participant. Presentation server (102) may record durations (958) of presentation of presented structural elements by timestamping each recording of identification and sequence and inferring duration from the difference between subsequent timestamps. Alternatively, presentation server (102) may be programmed to calculate the difference between the times of presentation of subsequent structural elements and record the differences as durations of presentation of presented structural elements.

For further explanation of recording (950), during the presentation, identities (956) of presented structural elements, durations (958) of presentation of presented structural elements, and sequence (960) of presentation of presented structural elements, FIG. 21 sets forth a chart illustrating an exemplary data structure useful for recording identities (956), durations (958), and sequence (960) of presentation of presented structural elements. The exemplary chart of FIG. 21 illustrates the actual presentation, sequence and duration, of a dozen structural elements. The description of a dozen structural elements is for explanation only, not a limitation of the present invention. Any number of structural elements may be presented in the scope of the present invention.

In the example of FIG. 21, the identities of the presented structural elements are recorded in column (956) in a fashion similar to the structural element identifiers in column (750) of the planned agenda of FIG. 20. In the example of FIG. 21, the actual sequence of presentation of the presented structural elements is recorded in column (960) as an incrementing integer, and the actual duration of presentation of each presented structural element is recorded in column (958).

Again with reference to FIG. 19: Readers will recognize that the actual presentation will vary from the planned agenda in content, in timing, and in sequence. The method of FIG. 19 therefore advantageously includes comparing (954) the planned agenda (962) with the recorded identities (956), durations (958), and sequence (960). That is, the method of FIG. 19 includes comparing (954) the planned agenda with the actual presentation.

In aid of such a comparison, presentation server (102) may be programmed to generate automatically a data structure similar to the one illustrated in FIG. 21. The structure of FIG. 21 contains not only the structural element identifications (956), sequence (960), and durations (958) of the actual presentation, but also the planned sequence (752) and durations (754) from the planned agenda for the presentation.

Comparing the planned agenda shows that only the first four presented structural elements are identical as planned and presented in sequence and also similar as planned and presented in duration. The first four presented structural elements were presented in the sequence as planned. The first four presented structural elements were presented with durations within a few tenths of a minute as planned. The planned durations for each were 3.0 minutes and the actual durations for each ranged between 2.5 minutes and 3.5 minutes.

Beginning with the fifth structural element presented, however, the element identified as ‘P5-S2,’ the actual presentation differs substantially from the planned agenda. Because actual presentations may vary so substantially from planned agendas, methods of dynamic differential content delivery that use a planned agenda according to embodiments of the present invention also may advantageously include analyzing a comparison of a planned agenda with recorded identities, durations, and sequence of an actual presentation. In such methods, analyzing the comparison of the planned agenda with the recorded identities, durations, and sequence may be carried out by contrasting the durations and sequence of presented structural elements according to the planned agenda with the durations and sequence as recorded.

Exemplary methods for analyzing and contrasting planned agendas with actual presentation are now explained with reference to FIGS. 21, 22, and 23, beginning with FIG. 22. FIG. 22 sets forth a bar chart generated under computer program control by a presentation server (102 on FIG. 19) using the planned and actual data (752, 754, 960, 958) from FIG. 21. The chart of FIG. 22 illustrates an exemplary method of contrasting the durations and sequence of presented structural elements according to the planned agenda with the durations and sequence as recorded. The chart of FIG. 22 is a graphic representation of a portion of the data from the table of FIG. 21. The chart of FIG. 22 sets forth twelve clusters (764) of four bars per cluster, one cluster for each row in the table of FIG. 21—so that each cluster of bars represents data analyzing an actual presentation of a structural element with respect to a planned agenda. Each cluster is labeled (766) with its corresponding data value from column (956) of FIG. 21 identifying a presented structural element, P1-S1, P1-S2, and so on.

As described in the cluster legend (878) of FIG. 22, each of the four bars in each of the twelve clusters represents respectively in order:

the planned sequence of presentation of a structural element,

the planned duration of presentation of the same structural element,

the actual sequence of presentation of the structural element, and

the actual duration of presentation of the structural element.

The planned duration bars represent 3.0 minutes across the chart. And the actual sequence bars represent a regular integer sequence across the chart, because the table of FIG. 22 is sorted on actual sequence. If the actual presentation followed the planned agenda precisely, therefore, the actual duration bars would all be the same height as the planned duration bars (all at 3 units height on this chart), and the planned sequence bars would all be the same height as their corresponding actual sequence bars (increasing integrally by one for each cluster across the chart).

It is immediately visually clear as analysis in this chart, however, that the planned sequence bar for the fifth cluster (‘P5-S2’) is much taller (value=12) than its corresponding actual sequence bar (value=5), and the actual duration bar for the fifth cluster is much taller (value=12) than its corresponding planned duration bar (value=3). In addition, it is also immediately visually clear as analysis in this chart that the planned sequence bar for the eighth cluster (‘P7-S1’) is much taller (value=15) than its corresponding actual sequence bar (value=8), and the actual duration bar for the eighth cluster is much taller (value=8) than its corresponding planned duration bar (value=3). In this analysis, both the fifth and the eight structural elements were presented out of the planned sequence and both of them had much longer actual presentation durations than planned durations. By this analysis, for future presentations, a presenter may, for example, advantageously break P5-S2 and P7-S1 into smaller segments and move them to earlier points in a planned sequence of a planned agenda.

Readers will notice that actual sequence bars in the chart of FIG. 22 increase steadily in height across the chart, as do also the planned sequence bars generally. In addition, planned duration and actual duration may vary very widely in value. The method of Chart 22, useful for small presentations, therefore, will usefully benefit from a method of normalizing data values to support analysis of presentations including hundreds or thousands of structural elements which may be presented for widely varying durations.

Such a method is illustrated with reference to FIGS. 21 and 23. The table of FIG. 21 includes a column (760) storing the ratio of planned sequence (752) to actual sequence (960) of presentation of structural elements. The table of FIG. 21 also includes a column (762) storing the ratio of planned duration (754) to actual duration (958) of presentation of structural elements. A presentation server (102 on FIG. 19) may be programmed to calculate and store such ratios (760, 762) at the time when actual sequence and duration data are stored—or later on the basis of such data stored earlier.

FIG. 23 sets forth a bar chart generated under computer program control by a presentation server (102 on FIG. 19) using the ratio data (760, 762) from FIG. 21. The bar chart of FIG. 23 illustrates an exemplary method of contrasting the durations and sequence of presented structural elements according to the planned agenda with the durations and sequence as recorded. The chart of FIG. 23 is a graphic representation of a portion of the data from the table of FIG. 21, that is, the ratio columns (760, 762). The chart of FIG. 23 sets forth twelve clusters (770) of two bars per cluster, one cluster for each row in the table of FIG. 21—so that each cluster of bars represents data analyzing an actual presentation of a structural element with respect to a planned agenda. Each cluster is labeled (766) with its corresponding data value from column (956) of FIG. 21 identifying a presented structural element, P1-S1, P1-S2, and so on. As described in the cluster legend (772) of FIG. 23, each of the two bars in each of the twelve clusters represents respectively in order:

the sequence ratio from column (760) of FIG. 21 and

the duration ratio from column (762) of FIG. 21.

In effect then, the first column in each cluster is a sequence analysis bar whose values are normalized around 1.0. When a planned sequence for a structural element is the same as its actual sequence number, then the value of its sequence ratio is 1.0, as is the case in the chart of FIG. 23 for structural elements P1-S1, P1-S2, P1-S3, and P2-S1. When an actual sequence of presentation for a structural element is earlier than its planned sequence, the sequence bar value for that structural element is greater than 1.0, as is the case for the structural elements P5-S2 and P7-S1. When an actual sequence of presentation for a structural element is later than its planned sequence, the sequence bar value for that structural element is less than 1.0, as is the case for the structural elements P2-S2, P2-S3, P3-S1, P3-S2, P3-S3, and P4-S1.

Similarly, the second column in each cluster is a duration analysis bar whose values are normalized around 1.0. When a planned duration for a structural element is the same as its actual duration, then the value of its duration ratio is 1.0, as is the case in the chart of FIG. 23 for structural elements P3-S3 and P4-S1. When an actual duration of presentation for a structural element is less than its planned duration, the duration bar value for that structural element is greater than 1.0, as is the case for the structural elements P1-S1, P1-S3, PS-S2, P2-S3, and P3-S1. When an actual duration of presentation for a structural element is less than its planned duration, the duration bar value for that structural element is less than 1.0, as is the case for the structural elements P1-S2, P2-S1, P5-S2, P7-S1, and P3-S2.

Normalizing sequence and duration ratio values around 1.0 makes for a chart in whose values fit on the chart sheet or display regardless of how many hundreds or thousands of structural elements are in a particular presentation. Moreover, normalizing ratios around 1.0 makes for a chart in which meaningful contrasts are immediately apparent. By the analysis of the chart of FIG. 23, P5-S2 and P7-S1 both occur earlier in actual sequence than planned, suggesting participant interest. In addition, both P5-S2 and P7-S1 occupied substantially longer actual durations than planned, further indicating participant interest. For future presentations, a presenter may therefore advantageously break P5-S2 and P7-S1 into smaller segments and move them to earlier points in a planned sequence of a planned agenda. Further by the analysis of the chart of FIG. 23, P2-S2 and P2-S3 both occupied substantially less actual duration than planned, suggesting lack of participant interest. A presenter therefore may advantageously consider combining P2-S2 and P2-S3 into a single structural element and presenting them both at the same time in a future presentation.

This specification has now explained several exemplary methods of comparing, analyzing, and contrasting planned agendas and actual presentations particularly with reference to FIGS. 19-23. These exemplary methods are for explanation, not for limitation of the invention. Readers of skill in the art will recognize that user classification data (706 on FIG. 19) may be included for analysis, adding an additional dimension to tables and charts such as the ones illustrated in FIGS. 21-23 thereby supporting analysis according to average participant technical level, for example. In such a case, give a particular comparison of a planned agenda and an actual presentation, the presentation may be structured differently in the future for marketing department personnel as opposed to participants from an engineering design department. In addition, other ways of comparing, analyzing, and contrasting planned agendas and actual presentations will occur to those of skill in the art, and all such ways are well within the scope of the present invention.

Differential Dynamic Content Delivery with Indications of Interest from Non-Participants

FIG. 24 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery with indications of interest from non-participants. FIG. 24 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery that includes providing (450) a session document (266) for a presentation. In the method of FIG. 24, the session document (266) includes a session grammar (258) and a session structured document (256). The session structured document (256) in this example includes at least one structural element (402) classified with at least one classification identifier (708), although readers will understand that as a practical matter the session structured document (256) typically will have many structural elements (402) classified with many classification identifiers (708). In this example, providing (450) a session document (266) for a presentation is carried out by creating a session document from a presentation document as described in detail above in the discussion regarding FIG. 16.

The method of FIG. 24 also includes recording (972) for a user not participating (982) in the presentation an associated indication of interest (284) in the selected structural element (456). Recording an indication of interest for a user not participating may be carried out in XML, for example, as follows:

<nonParticipantExpressionOfInterest>   <userName>Mike Jones</userName>   <keywords>sunspots radio propagation protons   ionosphere</keywords> </nonParticipantExpressionOfInterest> where a presentation server records a user name of a non-participating user as “Mike Jones” and records keywords representing indications of interest, “sunspots radio propagation protons ionosphere,” all wrapped in an XML element named “nonParticipantExpressionOfInterest.” Such indications of non-participant interest may be associated with a selected structural element by containing matching keywords. Keywords representing indications of non-participant interest may match text words inside a selected structural element. In the following expression of a selected structural element, for example:

<sessionStructuredDocument>   <page id=“1”>     <p id=“1”> a paragraph regarding sunspots</p>     <p id=“2”> another paragraph regarding sunspots</p>   </page> </sessionStructuredDocument> the structural element identified as page 1 of a session structured document includes two references to sunspots, which is one of the keywords representing indications of non-participant interest recorded in the example above for Mike Jones. In this sense, an indication of interest for a non-participant is associated with a selected structural element.

The method of FIG. 24 includes receiving (458) a presentation control instruction (460) in a presentation server (102) and selecting (452) from the session structured document (256) a classified structural element (402) having an associated indication of interest (284) from a user (982) not participating in the presentation. As discussed above, selecting (452) from a session structured document (256) a classified structural element (402) typically is also carried out in dependence upon user classifications (210 on FIG. 18) of a user participant (980) in the presentation. As also described above, a presentation control instruction (460) is an instruction to a presentation server (102) to carry out a particular presentation action such as, for example, ‘display next page,’ ‘display next slide,’ ‘display paragraph 5,’ and so on. In the method of FIG. 24, selecting (452) a classified structural element (402) is carried out by selecting a classified structural element (402) in dependence upon the presentation action identifier (518) and one or more parameters (520) from the presentation control instruction (460). In the method of FIG. 24, selecting (452) a classified structural element (402) also includes selecting a classified structural element having an associated classification identifier (708) that corresponds to the user classification (210 on FIG. 18).

The method of FIG. 24 includes detecting (976) whether classified structural element (402) has an associated indication of interest (284) from a user (982) not participating in the presentation. In this example, such detecting is carried out by determining whether the selected structural element contains text matching a text keyword in an indication of interest (284) from a user (982) not participating in the presentation.

The method of FIG. 24 also includes presenting (454) the selected structural element (456) to the user participant (980). In the method of FIG. 24, presenting (454) the selected structural element (456) to the user participant may be carried out, for example, by selecting a data communications protocol for the presentation, inserting the selected structural element (without its classification identifiers) in a data structure appropriate to the data communications protocol, and transmitting the data structure to the user according to the data communications protocol, all as described in more detail above with respect to the method of FIG. 18. As mentioned above, examples of data communications protocols useful for presenting selected structural elements according to embodiments of the present invention include HTTP, SIP, RTSP, RTTP, VoiceXML, and others as will occur to those of skill in the art.

For further explanation, consider the following exemplary session document:

<sessionDocument>   <sessionGrammar>     <grammarElement>       <contentType id=“WP”>       <keyPhrase>page down</keyPhrase>       <presentationAction id=“PgDn”>       <structuralElementIdentifier id=“page”>     </grammarElement >   </sessionGrammar>   <sessionStructuredDocument>     <page id=“1”>       <p id=“1”> a paragraph regarding sunspots</p>       <p id=“2”> another paragraph regarding sunspots</p>     </page>   <page id=“2”>     <p id=“2”>a paragraph on a particular subject</p>     <tech level=“2”>     <p id=“2”>a more technical paragraph, same subject</p>     </tech>     <company id=“IBM”>     <p id=“2”>a paragraph, same subject with added detail       pertinent to a user's company</p>     </company>     <p id=“3”>a paragraph on some other subject</p>     ... ... ...   </page>   </sessionStructuredDocument> </sessionDocument>

Assume that a non-participant has recorded in presentation server (102) an indication of interest as follows:

<nonParticipantExpressionOfInterest>   <userName>Mike Jones</userName>   <keywords>sunspots radio propagation protons   ionosphere</keywords> </nonParticipantExpressionOfInterest>

When the paragraphs of page 1 of the session structured document are presented to a participating user in a presentation, presentation server (102) is programmed to detect (976) whether they contain text matching keywords in an indication of interest from a user not participating in the presentation. If presentation server (102) detects no match, processing for the presentation continues normally (986).

If presentation server (102) detects a match (977), further processing includes several alternative. Presentation server (102) may, for example, notify (970) the user not participating (982) of the presentation (454) of the selected structural element (456). Notifying the non-participant may be carried out by email or instant messaging, for example, between the presentation server (102) and the non-participating user (982). The user not participating may be refraining from participating for a variety of reasons, including for example, uncertainty whether elements of interest are actually going to be presented during any particular presentation. So notifying (970) the user not participating (982) of the presentation (454) of the selected structural element (456) advantageously advises the non-participant that in fact a subject of interest to the non-participant is being presented. Knowing that in fact a subject of interest is actually being presented, a non-participant may wish to change his mind, log on, and view or otherwise participate in the presentation.

The method of FIG. 24 also includes notifying (974) the user not participating (982) of the identity of at least one user participant (980). Knowing who is participating may affect a non-participant's decision whether to participate. If the non-participant's expert colleague is already viewing the presentation, the user may feel no need to log on. If nobody from the user's department is viewing the presentation, the user may find it useful to log on, knowing now that a subject of interest is actually being presented. To support the non-participant in logging on and viewing the presentation if he wishes to do so, the method of FIG. 24 also includes allowing (978) the user not participating (982) to participate in the presentation, typically implemented, for example, by allowing the non-participant to log on late and join the presentation as a participant.

Differential Dynamic Content Delivery with a Session Document Recreated in Dependence Upon an Interest of an Identified User Participant

FIG. 25 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery with a session document recreated in dependence upon an interest of an identified user participant. FIG. 25 sets forth a data flow diagram illustrating an exemplary method for differential dynamic content delivery that includes creating (450) a session document (266) for a presentation. In the method of FIG. 25, the session document (266) includes a session grammar (258) and a session structured document (256). The session structured document (256) in this example includes at least one structural element (402) classified with at least one classification identifier (708), although readers will understand that as a practical matter the session structured document (256) typically will have many structural elements (402) classified with many classification identifiers (708).

In the example of FIG. 25, creating (450) a session document (266) for a presentation is carried out by creating a session document from a presentation document as described in detail above in the discussion regarding the method of FIG. 16. In the discussion regarding the method of FIG. 16, creating a session document is referred to as ‘providing a session document.’ As described in more detail below, the method of FIG. 25 includes recreating a session document based on received indications of interest from an identified participant in a presentation. ‘Recreating’ is more consonant with ‘creating’ than with ‘providing.’ For convenience of explanation, therefore, the terms ‘create,’ ‘creating,’ ‘recreate,’ and ‘recreating’ are used in explaining the method of FIG. 25.

In the method of FIG. 25, creating (450) a session document (266) includes identifying (252) a user participant (980) for the presentation. In this example, the user participant (980) has a user profile (126) comprising user classifications (210) and user interests (284). The user interests (284) are implemented as data fields for storing data values indicating user interest in one or more subjects of the presentation.

The method of FIG. 25 also includes receiving (850) from an identified user participant (980) a data value indicating user interest (852) in one or more subjects of the presentation. In the method of FIG. 25, receiving (850) from an identified user participant (980) a data value (852) indicating user interest in one or more subjects of the presentation is carried out by requesting (851) an expression of interest from an identified user participant (980) after creating (450) the session document (266) for the presentation. After creating (450) the session document (266) for the presentation (which includes identifying participants), the identities of participants are known, optionally including their email addresses. In the method of FIG. 25, therefore, requesting (851) an expression of interest from the identified user participant (980) after creating (450) the session document (266) for the presentation may include requesting the expression of interest by email. In addition, in the method of FIG. 25, receiving (850) from the identified user participant (980) at least one data value (852) indicating user interest in one or more subjects of the presentation further comprises receiving the data value by network data communications through a web site, by use of HTTP POSTs, HTML, or XML, for example, or through other data communications methods as may occur to those of skill in the art.

The method of FIG. 25 also includes storing (854) in the user profile the data value (852) indicating user interest. As described above regarding user classifications, a profile class (126 on FIG. 2) may include a string array storing user classifications (210). Examples of user classifications (210) include any supported data encoding describing users, including, for example, name-value pairs such as: “company=IBM,” “department=marketing,” “technical level=3,” “security level=2,” and others as will occur to those of skill in the art. Presentation server (102) therefore may be programmed according to embodiments of the present invention to store (854) in user profile (126) data values (852) indicating user interests as interests (284) encoded in user classifications (210). Data values indicating the user interests of ‘sunspots radio propagation protons ionosphere,’ for example, may be encoded in a string array of user classifications, such as the one illustrated at reference (210) on FIG. 2, as:

“userInterest=sunspots”

“userInterest=radio”

“userInterest=propagation”

“userInterest=protons”

“userInterest=ionosphere”

The method of FIG. 25 also includes recreating (856) the session document (266) in dependence upon the data value (852) indicating user interest. In the example of FIG. 25, recreating (856) a session document (266) for a presentation may be carried out by creating a session document from a presentation document as described in detail above in the discussion regarding the method of FIG. 16, including identifying a presentation document for the presentation where the presentation document includes a presentation grammar and a structured document having structural elements classified with classification identifiers, optionally identifying a user participant for the presentation where the user has a user profile comprising user classifications, and filtering the structured document in dependence upon the user classifications, the classification identifiers, and the data value indicating user interest. In the case of recreating the session document, however, the step of identifying a user participant is characterized as optional because the method typically uses the same participant list generated as part of identifying user participants when the session document was first created (450). To the extent that the process of recreating (856) the session document does use the same list of user participants as was used in first creating the session document and in requesting (851) and receiving (850) indications of interests, then indications of user interest (284) are part of the user classifications upon which the underlying structured document is filtered (reference 306 on FIG. 16). A session document so recreated now contains structural elements filtered in dependence upon not only the other user classifications in the pertinent user profiles, but also upon data indicating user interests.

The method of FIG. 25 also includes receiving (458) a presentation control instruction (460) in a presentation server and selecting (452) from a session structured document (256) a classified structural element (402) in dependence upon user classifications (210) of a user participant (124, 981, 980) in the presentation. As described above, a presentation control instruction (460) is an instruction to a presentation server (102) to carry out a particular presentation action such as, for example, ‘display next page,’ ‘display next slide,’ ‘display paragraph 5,’ and so on.

In the method of FIG. 25, selecting (452) a classified structural element (402) is carried out by selecting a classified structural element (402) in dependence upon a presentation action identifier (518) and parameters (520) from the presentation control instruction (460). In the method of FIG. 25, selecting (452) a classified structural element (402) also includes selecting a classified structural element having an associated classification identifier (708) that corresponds to a user classification (210). That is, selecting (452) from a session structured document (256) a classified structural element (402) in this example is carried out in dependence upon user classifications (210) of an identified user participant (980) in the presentation, and the user classifications of that participant include indications of his interests (284).

The method of FIG. 25 also includes presenting (454) the selected structural element (456) to users (124). In the method of FIG. 24, the users (124) to whom the selected structural element (456) is presented (454) may not be exactly the same users who were identified (980) during the initial creation of the session document (266). This is true because identifying additional user participants during the process of recreating (856) the session document is optional. If additional user participants are identified while recreating (856), the users (124) participating in the presentation may include users identified (980) during the initial creation of the session document (whose profiles now contain indications of their interests) as well as users (981) who were not identified during the initial creation (450) of the session document (266).

In the method of FIG. 25, presenting (454) the selected structural element (456) to the user participant may be carried out, for example, by selecting a data communications protocol for the presentation, inserting the selected structural element (without its classification identifiers) in a data structure appropriate to the data communications protocol, and transmitting the data structure to the user according to the data communications protocol, all as described in more detail above with respect to the method of FIG. 18. As mentioned above, examples of data communications protocols useful for presenting selected structural elements according to embodiments of the present invention include HTTP, SIP, RTSP, RTTP, VoiceXML, and others as will occur to those of skill in the art.

In view of the explanation set forth, readers will realize that the benefits of differential dynamic content delivery with a session document recreated in dependence upon interests of identified user participants is that presentations so developed may be focused more accurately upon the interests of the participants. It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims. 

1-10. (canceled)
 11. A system for differential dynamic content delivery, the system comprising at least one computer processor, at least one computer memory operatively coupled to the computer processor, and computer program instructions disposed within the computer memory capable of: creating a presentation document, including: creating, in dependence upon an original document, a structured document comprising one or more structural elements; classifying a structural element of the structured document according to a presentation attribute; and creating a presentation grammar for the structured document, wherein the presentation grammar for the structured document includes grammar elements each of which includes an identifier for at least one structural element of the structured document; creating a session document for a presentation, including identifying a user participant for the presentation, wherein the session document includes a session grammar and a session structured document, the user participant has a user profile comprising user classifications and user interests, the user interests comprising data fields for storing data values indicating user interest in one or more subjects of the presentation; wherein creating a session document further comprises creating the session document from the presentation document, including: identifying the presentation document for the presentation, the presentation document including a presentation grammar and a structured document having structural elements classified with classification identifiers; and filtering the structured document in dependence upon the user classifications and the classification identifiers; receiving from the identified user participant at least one data value indicating user interest in one or more subjects of the presentation; wherein receiving from the identified user participant at least one data value indicating user interest in one or more subjects of the presentation further comprises requesting an expression of interest from the identified user participant after creating the session document for the presentation; and wherein requesting an expression of interest from the identified user participant after creating the session document for the presentation further comprises requesting the expression of interest by email; and wherein the computer program instructions disposed within the computer memory are further capable of: storing in the user profile the data value indicating user interest; recreating the session document in dependence upon the data value indicating user interest; wherein recreating the session document further comprises recreating the session document from a presentation document, including: identifying a presentation document for a presentation, the presentation document including a presentation grammar and a structured document having structural elements classified with classification identifiers; optionally identifying a user participant for the presentation, the user having a user profile comprising user classifications; and filtering the structured document in dependence upon the user classifications, the classification identifiers, and the data value indicating user interest; creating a presentation control instruction, including: receiving from a user participating in the presentation a key phrase and optional parameters for invoking a presentation action; and parsing the key phrase and parameters against a voice response grammar into a presentation control instruction; and receiving the presentation control instruction, wherein the presentation control instruction includes a presentation action identifier and one or more optional parameters; and selecting from the recreated session document a classified structural element; and presenting the selected structural element to at least one user participant; wherein the at least one user participant to whom the selected structural element is presented is not the same as the identified user participant. 12-15. (canceled)
 16. A computer program product for differential dynamic content delivery, the computer program product embodied on a computer-readable medium, the computer program product comprising computer-implementable instructions capable of: creating a presentation document, including: creating, in dependence upon an original document, a structured document comprising one or more structural elements; classifying a structural element of the structured document according to a presentation attribute; and creating a presentation grammar for the structured document, wherein the presentation grammar for the structured document includes grammar elements each of which includes an identifier for at least one structural element of the structured document: creating a session document for a presentation, including identifying a user participant for the presentation, wherein the session document includes a session grammar and a session structured document, the user participant has a user profile comprising user classifications and user interests, the user interests comprising data fields for storing data values indicating user interest in one or more subjects of the presentation; wherein creating a session document further comprises creating the session document from the presentation document, including: identifying the presentation document for the presentation, the presentation document including a presentation grammar and a structured document having structural elements classified with classification identifiers; and filtering the structured document in dependence upon the user classifications and the classification identifiers; receiving from the identified user participant at least one data value indicating user interest in one or more subjects of the presentation; wherein receiving from the identified user participant at least one data value indicating user interest in one or more subjects of the presentation further comprises requesting an expression of interest from the identified user participant after creating the session document for the presentation; and wherein requesting an expression of interest from the identified user participant after creating the session document for the presentation further comprises requesting the expression of interest by email; and wherein the computer-implementable instructions are further capable of: storing in the user profile the data value indicating user interest; recreating the session document in dependence upon the data value indicating user interest; wherein recreating the session document further comprises recreating the session document from a presentation document, including: identifying a presentation document for a presentation, the presentation document including a presentation grammar and a structured document having structural elements classified with classification identifiers; optionally identifying a user participant for the presentation, the user having a user profile comprising user classifications; and filtering the structured document in dependence upon the user classifications, the classification identifiers, and the data value indicating user interest; creating a presentation control instruction, including: receiving from a user participating in the presentation a key phrase and optional parameters for invoking a presentation action; and parsing the key phrase and parameters against a voice response grammar into a presentation control instruction; and receiving the presentation control instruction, wherein the presentation control instruction includes a presentation action identifier and one or more optional parameters; and selecting from the recreated session document a classified structural element; and presenting the selected structural element to at least one user participant; wherein the at least one user participant to whom the selected structural element is presented is not the same as the identified user participant. 17-20. (canceled) 